Characterizing and imaging gross and real finger contacts under dynamic loading

We describe an instrument intended to study finger contacts under tangential dynamic loading. This type of loading is relevant to the natural conditions when touch is used to discriminate and identify the properties of the surfaces of objects — it is also crucial during object manipulation. The system comprises a high performance tribometer able to accurately record in vivo the components of the interfacial forces when a finger interacts with arbitrary surfaces which is combined with a high-speed, high-definition imaging apparatus. Broadband skin excitation reproducing the dynamic contact loads previously identified can be effected while imaging the contact through a transparent window, thus closely approximating the condition when the skin interacts with a non-transparent surface during sliding. As a preliminary example of the type of phenomenon that can be identified with this apparatus, we show that traction in the range from 10 to 1000 Hz tends to decrease faster with excitation frequency for dry fingers than for moist fingers

Fine-grained semi-automated runtime evolution

Modern software systems that play critical roles in society are often required to change at runtime so that they can continuously provide essential services in the dynamic environments they operate in. Updating open, distributed software systems at runtime is very challenging. Using runtime models as an interface for updating software at runtime can help developers manage the complexity of updating software while it is executing. In this chapter we describe an approach to updating Java software at runtime through the use of runtime models consisting of UML class and sequence diagrams. Changes to models are transformed to changes on Java source code, which is then propagated to the runtime system using the JavAdaptor technology. In particular, the presented approach permits in-the-small software changes, i.e., changes at the code statement level, as opposed to in-the-large changes, i.e., changes at the component level. We present a case study that demonstrates the major aspects of the approach and its use. We also give the results of a preliminary evaluation of the approach

Constraint Support in MDA tools: a Survey

Abstract: The growing interest in the MDA (Model-Driven Architecture) and MDD (Model-Driven Development) approaches has largely increased the number of tools and methods including code-generation capabilities. Given a platform-independent model (PIM) of an application, these tools generate (part of) the application code either by defining first a platform-specific model or by executing a direct PIM to code transformation. However, current tools present several limitations regarding code generation of the integrity constraints defined in the PIMs. This paper compares these tools and shows that they lack expressiveness in the kind of constraints they can handle or efficiency in the code generated to verify them. Based on this evaluation, the features of an ideal code-generation method for integrity constraints are established. We believe such a method is required to extend MDA adoption in the development of industrial projects, where constraints play a key role. 1

From Declarative to Imperative UML/OCL Operation Specifications

An information system maintains a representation of the state of the domain in its Information Base (IB). The state of the IB changes due to the execution of the operations defined in the behavioral schema. There are two different approaches for specifying the effect of an operation: the imperative and the declarative approaches. In conceptual modeling, the declarative approach is preferable since it allows a more abstract and concise definition of the operation effect and conceals all implementation issues. Nevertheless, in order to execute the conceptual schema, declarative specifications must be transformed into equivalent imperative ones. Unfortunately, declarative specifications may be non-deterministic. This implies that there may be several equivalent imperative versions for the same declarative specification, which hampers the transformation process. The main goal of this paper is to provide a pattern-based translation method between both specification approaches. To facilitate the translation we propose some heuristics that improve the precision of declarative specifications and help avoid non-determinism in the translation process